Onboarding

API

An API works to provide a communication link between the merchants’ server and Moneris’ server. API’s are required to complete any transaction, and therefore the API for Google Pay™ is also included within an SDK. If the merchant chooses to use only an API the merchant must decrypt payload information themselves before sending the decrypted information to the Moneris Gateway to be processed. Because this process is complicated, Google recommends only businesses with expertise and a previously integrated payment processing system use APIs instead of SDKs.

Note: In the API scenario where merchant’s server is responsible for decrypting the payload, merchants must sign agreement with Google directly. Google can then provide you with the keys to decrypt the payload.

SDK

SDKs are ready-to-install kits containing APIs as well as additional tools for development. SDKs contain the tools to develop the standard features merchants require. These include features like purchase, pre-authorization, refund*, completion* and void* transactions. During transactions, merchants that choose to use an SDK only pass along the encrypted payload they receive from Google to the Moneris Gateway. Moneris then decrypts and processes the transaction. This method makes the transaction process simple for the merchant, and is therefore well suited for small to medium sized businesses.

Both methods of integration are equally secure for the customer, as well as the merchant. Merchants and developers should determine which method is more appropriate for their app.

refund, completion and void transactions will be supported, but no data is required from Google and the transaction should be implemented on the merchants server.